Forecasting time-independent search queries

ABSTRACT

Techniques for analyzing and modeling the frequency of queries are provided by a query analysis system. A query analysis system analyzes frequencies of a query over time to determine whether the query is time-dependent or time-independent. The query analysis system forecasts the frequency of time-dependent queries based on their periodicities. The query analysis system forecasts the frequency of time-independent queries based on causal relationships with other queries. To forecast the frequency of time-independent queries, the query analysis system analyzes the frequency of a query over time to identify significant increases in the frequency, which are referred to as “query events” or “events.” The query analysis system forecasts frequencies of time-independent queries based on queries with events that tend to causally precede events of the query to be forecasted.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to U.S. patent application Ser. No. ______ (Attorney Docket No. 418268429US) entitled “Determination of Time Dependency of Search Queries,” U.S. patent application Ser. No. ______ (Attorney Docket No. 418268429US1) entitled “Forecasting Time-Dependent Search Queries,” U.S. patent application Ser. No. ______ (Attorney Docket No. 418268429US2) entitled “Identification of Events of Search Queries,” and U.S. patent application Ser. No. ______ (Attorney Docket No. 418268429US4) entitled “Forecasting Search Queries Based on Time Dependencies,” which are being filed concurrently and which are hereby incorporated by reference in their entireties.

BACKGROUND

Many search engine services, such as Google and Yahoo, provide for searching for information that is accessible via the Internet. These search engine services allow users to search for display pages, such as web pages, that may be of interest to users. After a user submits a search request (i.e., a query) that includes search terms, the search engine service identifies web pages that may be related to those search terms. To quickly identify related web pages, the search engine services may maintain a mapping of keywords to web pages. This mapping may be generated by “crawling” the web (i.e., the World Wide Web) to identify the keywords of each web page. To crawl the web, a search engine service may use a list of root web pages to identify all web pages that are accessible through those root web pages. The keywords of any particular web page can be identified using various well-known information retrieval techniques, such as identifying the words of a headline, the words supplied in the metadata of the web page, the words that are highlighted, and so on. The search engine service identifies web pages that may be related to the search request based on how well the keywords of a web page match the words of the query. The search engine service then displays to the user links to the identified web pages in an order that is based on a ranking that may be determined by their relevance to the query, popularity, importance, and/or some other measure.

Search engine services obtain revenue by placing advertisements along with search results. These paid-for advertisements are commonly referred to as “sponsored links,” “sponsored matches,” or “paid-for search results.” An advertiser who wants to place an advertisement (e.g., a link to their web page) along with certain search results provides a search engine service with an advertisement and one or more bid terms. When a search request is received, the search engine service identifies the advertisements whose bid terms match the terms of the search request. The search engine service then selects advertisements to display based on the closeness of their match, the amount of money that the advertisers are willing to pay for placing the advertisement, and other factors. The search engine service then adds a sponsored link to the search result that points to a web page of the advertiser. The search engine services typically either charge for placement of each advertisement along with search results (i.e., cost per impression) or charge only when a user actually selects a link associated with an advertisement (i.e., cost per click).

Advertisers would like to maximize the effectiveness of their advertising dollars used to pay for advertisements. Thus, advertisers try to identify bid term, advertisement, and bid amount combinations that result in the highest benefits (e.g., most profit) to the advertiser. Advertisers may analyze query trends to identify bid terms, timing for placing advertisements based on those bid terms, bid amounts for those bid terms, and so on. Query trend analysis studies how the frequency of queries changes over time and is used to predict the future frequency of queries. If query trends can be accurately predicted, then advertisers can adjust their placement of advertisements in an attempt to maximize the advertising effectiveness. For example, if a query is likely to increase in the near future, an advertiser may want to increase the bid amount for terms of that query. It has been, however, difficult to accurately model the frequency of queries.

SUMMARY

Techniques for analyzing and modeling the frequency of queries are provided by a query analysis system. A query analysis system analyzes frequencies of a query over time to determine whether the query is time-dependent or time-independent. The frequency of a time-dependent query is likely to vary with a certain periodicity or multiple periodicities. A time-independent query, in contrast, tends to have no observable correlation with time. The query analysis system forecasts the frequency of time-dependent queries based on their periodicities. The query analysis system forecasts the frequency of time-independent queries based on causal relationships with other queries. To forecast the frequency of time-independent queries, the query analysis system analyzes the frequency of a query over time to identify significant increases in the frequency, which are referred to as “query events” or “events.” To assist a user in determining the cause of an event for a query, the query analysis system may display an indication of the top search results that were selected by searchers who submitted that query. The query analysis system may also generate graphs of the frequency of a query that indicate the past frequency of the query and the forecasted or predicted frequency of the query for both time-dependent queries and time-independent queries.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a graph of past and predicted frequencies.

FIG. 2 illustrates a graph of past and predicted frequencies along with an indication of the periodicity of the query.

FIG. 3 illustrates a graph of past and predicted frequencies along with clickthrough information.

FIG. 4 illustrates a graph of past and predicted frequencies along with clickthrough data for a range of intervals.

FIG. 5 illustrates a graph of past and predicted frequencies for multiple queries with clickthrough data.

FIG. 6 is a block diagram that illustrates components of the query analysis system in some embodiments.

FIG. 7 is a block diagram that illustrates the logical organization of a data structure of the query frequency store in some embodiments.

FIG. 8 is a flow diagram that illustrates the processing of a create query model component of the query analysis system in some embodiments.

FIG. 9 is a flow diagram that illustrates the processing of a determine time dependency component of the query analysis system in some embodiments.

FIG. 10 is a flow diagram that illustrates the processing of the identify peaks component of the query analysis system in some embodiments.

FIG. 11 is a flow diagram that illustrates the processing of the generate time-dependent query model component of the query analysis system in some embodiments.

FIG. 12 is a flow diagram that illustrates the processing of an identify causal queries component of the query analysis system in some embodiments.

FIG. 13 is a flow diagram that illustrates the processing of the identify events component of the query analysis system in some embodiments.

FIG. 14 is a flow diagram that illustrates the processing of the identify candidate events component of the query analysis system in some embodiments.

FIG. 15 is a flow diagram that illustrates the processing of the merge candidate events component of the query analysis system in some embodiments.

FIG. 16 is a flow diagram that illustrates the processing of the split candidate events component of the query analysis system in some embodiments.

FIG. 17 is a flow diagram that illustrates the processing of the calculate query causal score component of the query analysis system in some embodiments.

FIG. 18 is a flow diagram that illustrates the processing of the calculate event/query score component of the query analysis system in some embodiments.

FIG. 19 is a flow diagram that illustrates the processing of a display frequency graph component of the query analysis system in some embodiments.

FIG. 20 is a flow diagram that illustrates the processing of the display event explanation component of the query analysis system in some embodiments.

FIG. 21 is a flow diagram that illustrates the processing of the predict frequency for time-dependent query component of the query analysis system in some embodiments.

FIG. 22 is a flow diagram that illustrates the processing of the predict frequency for time-independent query component of the query analysis system in some embodiments.

DETAILED DESCRIPTION

Techniques for analyzing and modeling the frequency of queries are provided by a query analysis system. In some embodiments, a query analysis system analyzes frequencies of a query over time to determine whether the query is time-dependent or time-independent. The frequency of a time-dependent query is likely to vary with a certain periodicity or multiple periodicities. A time-independent query, in contrast, tends to have no observable correlation with time. For example, the query “Christmas gift” is likely to have a periodicity of one year and is thus time-dependent, while the query “Harry Potter” may have no discernible periodicity and is thus time-independent. The query analysis system forecasts the frequency of time-dependent queries based on their periodicities. The query analysis system forecasts the frequency of time-independent queries based on causal relationships with other queries. For example, the query “Asian tsunami” may be causally related to the query “Asian map.” Analysis of the frequency of the query “Asian map” indicates that it has increased dramatically as the frequency of the query “Asian tsunami” has increased. In particular, the query “Asian tsunami” became very popular in late December 2004 because many users submitted that query to obtain information about the recent Asian tsunami. To forecast the frequency of time-independent queries, the query analysis system analyzes the frequency of a query over time to identify significant increases in the frequency, which are referred to as “query events” or “events.” For example, an event occurred in late December 2004 for the query “Asian tsunami.” To assist a user in determining the cause of an event for a query, the query analysis system may display an indication of the top search results that were selected by searchers who submitted that query. For example, in the case of the query “Asian tsunami,” the top search results selected by the searchers were links to web pages with news stories describing the tsunami. The query analysis system may also generate graphs of the frequency of a query that indicate the past frequency of the query and the forecasted or predicted frequency of the query for both time-dependent queries and time-independent queries.

In some embodiments, the query analysis system determines the time dependency of a query by analyzing the frequency of the query over time. Because the query analysis system analyzes the frequency of the query itself, the analysis is referred to as an internal analysis that only considers factors internal to the query itself. The query analysis system calculates the value of the frequency spectral for the frequencies of the queries at various angular frequencies. The value of the frequency spectral for an angular frequency measures the occurrences of the frequency of the query at that angular frequency. For example, for the query “Christmas gift,” the value of the frequency spectral for the angular velocity corresponding to 365 days will likely be large, indicating that the frequency of the query increases with a periodicity of 365 days. After generating the values of the frequency spectral, the query analysis system analyzes the values, identifying peaks indicating an angular frequency at which the frequency of the query increases. Each peak may correspond to a periodicity of the query. If the query analysis system identifies at least one peak, then it may designate the query as a time-dependent query. If the query analysis system does not identify any peaks, then it may designate the query as a time-independent query.

In some embodiments, the query analysis system uses a time-dependent query model that is based on the periodicities of a time-dependent query to forecast the frequency of query. For each periodicity of a time-dependent query, the query analysis system generates various parameters for that periodicity for the model. These parameters may be based on the angular frequency, the amplitude of the angular frequency, and the phase of the angular frequency. The query analysis system may also assess the accuracy of the model by comparing actual frequencies to frequencies predicted by the model. If the accuracy of the model for a query is high, the query analysis system uses the parameters of the periodicities of the query to predict future frequencies of the query. If the accuracy is low, then the query analysis system may indicate that the frequency of the query cannot be accurately predicted based on its time dependency. In such a case, the query analysis system may attempt to forecast the frequency of the query using a time-independent query model.

In some embodiments, the query analysis system forecasts a time-independent query based on analysis of its causal relationship with other queries. Since this analysis is based on other queries, it is referred to as an external analysis based on external factors. To generate a time-independent query model for a target query, the query analysis system generates a query causal score for pairs of queries that include the target query and another query. A query causal score measures the likelihood that the other query of the pair causes the target query. The query analysis system generates a query causal score for a pair of queries by identifying the events within each query and generating an event causal score that measures the likelihood that an event of the other query has a causal relationship with an event of the target query. The query analysis system then aggregates the event causal scores to generate the query causal score. The queries with high query causal scores are candidate queries to be the likely cause of the target query.

In some embodiments, the query analysis system generates a time-independent query model for forecasting time-independent queries based on the frequencies of the candidate queries that are likely to be the cause of the target query. The query analysis system may use a multiple regression technique to generate a weight for each candidate query indicating its overall influence on the frequency of the target query. For example, a candidate query with a relatively low causal relationship may have a weight of 0.01, whereas a candidate query with a relatively high causal relationship may have a weight of 0.4. The query analysis system then uses weights for a target query and the frequencies of the candidate queries to predict the frequency of the target query. To predict the frequency, the query analysis system retrieves the frequencies for the candidate queries and generates a weighted sum of those frequencies as the predicted frequency of the target query.

The query analysis system may extract the count or frequency of queries from a query log for an interval (e.g., a day). The query analysis system represents each query Q by a time series Q={q₁, q₂, . . . , q_(N)}, where N is the length of the time series and q_(i) , is the query frequency on the ith interval. One skilled in the art will appreciate that the interval may be a day, more than a day (e.g., two days or seven days), or less than a day (e.g., 12 hours) depending on the goals of the query analysis system.

In some embodiments, the query analysis system uses a cosine signal hidden periodicity (“CSHP”) model to determine the time dependency of a query. The CSHP model may be represented as follows:

$\begin{matrix} {q_{t} = {{\sum\limits_{j = 1}^{k}{A_{j}{\cos \left( {{\omega_{j}t} + \phi_{j}} \right)}}} + \xi_{t}}} & (1) \end{matrix}$

where A_(j) represents the amplitude of the angular velocity ω_(j) for angular frequency j, φ_(j) represents the phase of the angular velocity ω_(j) for angular frequency j, and ξ₁ represents background noise. The periodicities of q₁ are represented as follows:

T _(j)=2π/ω_(j) ,j=1,2, . . . ,k   (2)

(See Box, G., Jenkins, G. M., Reinsel, G., “Time Series Analysis, Forecasting and Control,” Prentice Hall, 1994; Chatfield, C., “The Analysis of Time Series: An Introduction,” Chapman & Hall/CRC, 1996; and Enders, W., “Applied Econometric Time Series,” Wiley, 2003.)

In some embodiments, to simplify parameter estimation, the query analysis system extends the model to the complex domain as represented by the following:

$\begin{matrix} {{q_{t} = {{\sum\limits_{j = 1}^{q}{\alpha_{j}{\exp \left( {\; t\; \lambda_{j}} \right)}}} + \xi_{t}}}{where}{{q = {2k}},{\lambda_{j}\left\{ {\begin{matrix} \omega_{j} & {{j = 1},2,\ldots \mspace{11mu},k} \\ {- \omega_{j - k}} & {{j = {k + 1}},{k + 2},\ldots \mspace{11mu},k} \end{matrix}\alpha_{j}\left\{ \begin{matrix} {\frac{1}{2}A_{j}{\exp \left( {\phi}_{j} \right)}} & {{j = 1},2,\ldots \mspace{11mu},k} \\ {\frac{1}{2}A_{j - k}{\exp \left( {- {\phi}_{j - k}} \right)}} & {{j = {k + 1}},{k + 2},\ldots \mspace{11mu},q} \end{matrix} \right.} \right.}}} & (3) \end{matrix}$

For a time series {q₁, q₂, . . . , q_(N)}, the value frequency spectral of the model is represented by the following:

$\begin{matrix} {{S_{N}(\lambda)} = {{\sum\limits_{t = 1}^{N}{q_{t}^{{- }\; \lambda \; t}\lambda}} \in \left\lbrack {{- \pi},\pi} \right\rbrack}} & (4) \end{matrix}$

The number of peaks in the frequency spectral is an estimate of the number of periodicities, and a peak is a local maximum of the values of the frequency spectral as represented by the following:

S_(N)(λ_(j))≧S_(N)(λ),

where λε[λ_(j)−1/2√{square root over (N)}, λ_(j)+1/2√{square root over (N)}]  (5)

λ_(j), j=1,2, . . . , k represents the angular frequency of the peaks.

To generate a time-dependent query model for a query, the query analysis system estimates the parameters for the model as follows:

$\begin{matrix} {{\omega_{j\;} = \lambda_{j}^{*}},{T_{j} = {{2{\pi/\omega_{j}}} = {2{\pi/\lambda_{j}^{*}}}}},{\alpha_{j} = {\sum\limits_{t = 1}^{N}{q_{t}^{{- {\lambda}_{j}^{*}}t}}}},{A_{j} = {{2{\alpha_{j}}\mspace{14mu} {and}\mspace{14mu} \phi_{j}} = {\arg \left( \alpha_{j} \right)}}}} & (6) \end{matrix}$

where λ_(j)* represents the angular frequency of the jth peak. The query analysis system may identify the peaks of the frequency spectral of a query as represented by the pseudocode of Table 1.

TABLE 1 1. Calculate the mean of Q = {q₁, q₂, . . . , q_(N)} as  $\overset{\_}{Q} = {\frac{1}{N}{\sum\limits_{t = 1}^{N}\; q_{t}}}$ 2. Centralize Q to a zero mean time series as x₁ = q₁ − Q, t = 1, 2, . . . , N 3. Identify peaks within the frequency spectral 4. If the frequency spectral has k peaks, output the periodicity T₁, else indicate that the query is time-independent

Analysis of the frequency spectral for the query “Christmas gifts” indicates that there is a peak at an angular frequency of 0.018 with a periodicity as represented by the following:

T= ^(2π) _(/0.018)≈365   (7)

The query analysis system predicts the frequency of a time-dependent query using Equation 1 and the parameters generated for each periodicity of the query. The query analysis may check the accuracy of the time-dependent model for a query by comparing actual frequencies to predicted frequencies as represented by the pseudocode of Table 2.

TABLE 2 1. Estimate parameter of Equation 3 2. Calculate the predicted frequencies {circumflex over (Q)} = {{circumflex over (q)}₁, {circumflex over (q)}₂, . . . , {circumflex over (q)}_(N)} using Equation 3 3. Calculate a reconstruction error as   ${RE} = \frac{\frac{1}{N}{\sum\limits_{t = 1}^{N}\; \left( {q_{t} - {\hat{q}}_{t}} \right)^{2}}}{\frac{1}{k}{\sum\limits_{j = 1}^{k}\; A_{j}}}$

The reconstruction error (“RE”) represents a measure of the accuracy of the time-dependent query model for a query. If the reconstruction error is small, then the query analysis system uses the model to predict the frequency of the query.

In some embodiments, the query analysis system models the frequency of time-independent queries based on analysis of causally related queries. If the change in the frequency of one query consistently causes the frequency of another query to change within a time period, then the queries are causally related. The query analysis system may represent the causal relationship between two queries A and B as follows:

A<B   (8)

where A causally precedes B. Causal relatedness is asymmetric in the sense that if A causally precedes B , then it is unlikely that B will causally precede A. Many techniques have been proposed for analyzing the causal relationship between variables. One such technique is the Granger Causality Test. (See Frankes, W. B. and Baeza-Yates, R., “Information Retrieval: Data Structures and Algorithms,” Prentice Hall PTR, 1992.) Although such techniques may identify causally related variables with a high degree of confidence, these techniques are computationally expensive. For example, the computational complexity of determining the causal relatedness of queries may be O(mn²), where m represents the length of the time series and n represents the number of queries.

To avoid this computational complexity, the query analysis system, in some embodiments, represents each query as a sequence of query events. An event for a query occurs when a significant increase in the frequency of the query occurs over one or more intervals. The query analysis system then calculates a query causal score as a measurement of the degree to which a first query causally precedes a second query by aggregating event/query causal scores. An event/query causal score measures the degree to which a first event of the first query causally precedes second events of the second query. An event/query causal score may be a maximum of event causal scores that measures the degree to which a first event of the first query causally precedes a second event of the second query.

The query analysis system may identify events of a query when the frequency in a sequence of one or more intervals satisfies a baseline criterion and at least one of the frequencies in the sequence satisfies a climax criterion. For example, the baseline criterion may be that the frequencies of the sequence are above a baseline threshold f_(b), and the climax criterion may be that the frequency of an interval is above a climax threshold frequency f_(c). The query analysis system may designate the ith event of a query as e_(iq). The query analysis system may represent a query as a sequence of events as follows:

Q={e₁ ^(Q), e₂ ^(Q), . . . , e_(M) ^(Q)}  (9)

with each event being represented as follows:

e^(q=<id, t) _(b), t_(e), t_(c), ts_(c)>  (10)

where id represents the identifier of the event, t_(b) and t_(e) represent the start and end time of the event and specify the event period, t_(c) represents the time of the climax, and ts_(c) represents the frequency of the climax. The length of the event may be represented as t_(e)−t_(b), and the importance of the event may be represented as (t_(e)−t_(b))*ts_(c). The query analysis system represents the area of an event as a measure of importance of the event as follows:

$\begin{matrix} {{S\left( ^{q} \right)} = {\frac{1}{2}\left( {t_{e} - t_{b}} \right) \times {ts}_{c}}} & (11) \end{matrix}$

The sequence of events of a query may be considered a feature vector representing the query. The generating of a time-independent query model based on feature vectors thus represents a reduction in the dimensionality over conventional techniques that determine causal relatedness of variables. The query analysis system may identify events of a query as presented by the pseudocode of Table 3.

TABLE 3 1. Detect candidate events using a 3σ rule of Gaussian distribution 2. Merge candidate events that share substantially the same event period 3. Split candidate events that have a deep valley between climaxes

The query analysis system may represent an event causal score as a probability of event e₁ causing event e₂ by the following:

$\begin{matrix} {{P\left( {e_{1} \prec e_{2}} \right)} = \left\{ \begin{matrix} 0 & {{if}\mspace{14mu} {t_{b}\left( e_{1} \right)}\mspace{14mu} {after}\mspace{14mu} {t_{b}\left( e_{2} \right)}} \\ \frac{{S\left( e_{1} \right)}\bigcap{S\left( e_{2} \right)}}{\max \left( {{S\left( e_{1} \right)},{S\left( e_{2} \right)}} \right)} & {else} \end{matrix} \right.} & (12) \end{matrix}$

where S(e₁) represents the area of event e_(i). The larger the area of the event and the larger its climax, the more important the event. The query analysis system represents the query causal score that a query A causes query B by the following:

$\begin{matrix} \begin{matrix} {{P\left( {A \prec B} \right)} = \frac{\sum\limits_{i = 1}^{M^{A}}{{S\left( e_{i}^{A} \right)}{P\left( {e_{i}^{A} \prec B} \right)}}}{\sum\limits_{i = 1}^{M^{A}}{S\left( e_{i}^{A} \right)}}} \\ {= \frac{\sum\limits_{i = 1}^{M^{A}}{{S\left( e_{i}^{A} \right)}{\max\limits_{1 \leq j \leq M^{B}}{P\left( {e_{i}^{A} \prec e_{j}^{B}} \right)}}}}{\sum\limits_{i = 1}^{M^{A}}{S\left( e_{i}^{A} \right)}}} \end{matrix} & (13) \end{matrix}$

where A={e₁ ^(A), e₂ ^(A), . . . , e_(M) ^(A) ^(A}, B={e) ₁ ^(B, e) ₂ ^(B), . . . , e_(M) ^(B) ^(B)}, and M^(A) represents the number of events in query A. The query analysis system represents the importance of an event to a query as the size of the area of the event relative to the aggregate size of the areas of the events of the query. The event/query causal score for the combination of an event of query A and the query B is the maximum event causal score for that event of query A and each event of query B. Therefore, the query causal score is an aggregation of the probabilities of events of query A causing events of query B weighted by the importance of the events of query A.

In some embodiments, the query analysis system generates a time-independent query model for forecasting query frequencies by combining frequencies of candidate queries that are identified as queries that are causally related to a target query whose frequency is to be forecasted. The query analysis system may represent a time series of a query to be forecasted as Q={q₁, q₂, . . . , q_(N)} and candidate queries as {C₁, C₂, . . . , C_(n)}. The time series of each candidate query may be represented as C_(i)={C_(i1), C_(i2), . . . , C_(iN)}. The query analysis system may use a multiple regression model to learn the weights of the candidate queries for the time-independent query model of the query as represented by the following:

Q=β _(0+β) ₁ C _(1+β) ₂ C ₂+ . . . +β_(n) C _(n+ξ)  (14)

where ξ represents background noise and β_(i) represents the weight of the ith candidate query. The query analysis system sets parameters of the time-independent query model as the candidate queries along with their weights. The query analysis system calculates the weights by solving the linear equations as represented by the following:

$\begin{matrix} \left\{ \begin{matrix} {q_{1} = {\beta_{0} + {\beta_{1}c_{11}} + {\beta_{2}c_{21}} + {{\ldots++}\beta_{n}C_{n\; 1}}}} \\ {q_{N} = {\beta_{0} + {\beta_{1}c_{1\; N}} + {\beta_{2}c_{2N}} + {{\ldots++}\beta_{n}C_{nN}}}} \end{matrix} \right. & (15) \end{matrix}$

To generate a prediction of the frequency of the target query for an interval, the query analysis system retrieves the frequencies of the candidate queries for that interval and sets the predicted frequency to the weighted sum of the frequencies of the candidate queries as represented by Equation 14.

FIGS. 1-5 are display pages illustrating graphs of the query analysis system in some embodiments. FIG. 1 illustrates a graph of past and predicted frequencies. A display page 100 includes a query field 101 and a graph 102. After a user enters a query into the query field, the query analysis system generates and displays the graph of the frequency for the query. The x-axis of the graph represents the intervals, and the y-axis represents the frequencies. The portion 103, which may be highlighted (e.g., shaded), indicates the interval for which the frequency for the query was predicted.

FIG. 2 illustrates a graph of past and predicted frequencies along with an indication of the periodicity of the query. A display page 200 includes a query field 201 and a graph 202. After a user enters a query into the query field, the query analysis system generates and displays the graph of the frequency for the query. The portion 203 indicates an interval for which the frequency for the query was predicted. The shaded portions 204 indicate the periodicity of the query. The query analysis may display a radio button for each periodicity of the query so that a user can view a graph with the different periodicity indicated.

FIG. 3 illustrates a graph of past and predicted frequencies along with clickthrough information. A display page 300 includes a query field 301, a graph 302, and clickthrough information 306. After a user enters a query into the query field, the query analysis system generates and displays the graph of the frequency for the query and clickthrough information. The portion 303 indicates an interval for which the frequency for the query was predicted. The user may select an interval 305 to display for the clickthrough data 306 for the query during that interval. The clickthrough data indicates the top search result items (e.g., their URLS) of that query that were selected by the searchers during that interval along with a count of the number of times each item was selected. The clickthrough data provides the user with information that may indicate why the searchers submitted the query or the type of information that the searchers were seeking.

FIG. 4 illustrates a graph of past and predicted frequencies along with clickthrough data for a range of intervals. A display page 400 includes a query field 401, a graph 402, and clickthrough data 406. After a user enters a query into the query field, the query analysis system generates and displays the graph of the frequency for the query. The portion 403 indicates an interval for which the frequency for the query was predicted. The user may select an interval range 405 a to 405 b to display an indication of the clickthrough data 406 for the query during that range of intervals. The clickthrough data indicates the top search results items (e.g., their URLs) of the search results of that query that were selected by the searchers during the interval at the start of the range. The clickthrough data also includes arrows for each interval of the range indicating whether the frequency of selection of items of the search results for the query increased or decreased from the previous interval and may indicate whether the change was significant by, for example, the color of the arrow. The arrows are referred to as an interval trend chart.

FIG. 5 illustrates a graph of past and predicted frequencies for multiple queries with clickthrough data. A display page 500 includes a query field 501, a graph 502, and clickthrough data 506 for two queries. After a user enters a second query into the query field, the query analysis system generates and displays the graph of the frequency for both queries. The portion 503 indicates an interval for which the frequencies for the queries are predicted. The user may select an interval range 505 a to 505 b to display an indication of the clickthrough data 506 for each of the queries during that range of intervals.

FIG. 6 is a block diagram that illustrates components of the query analysis system in some embodiments. The query analysis system 610 may be connected to a search engine 650, web servers 660, and user computing devices 670 via the communications link 640. The query analysis system includes various data stores including a clickthrough log store 611, a query frequency store 612, a time-dependent parameter store 613, and a time-independent parameter store 614. The clickthrough log store contains clickthrough data collected from the search engine. The query frequency store contains the frequency of each query at each interval. The time-dependent parameter store contains the parameters for each query for the time-dependent query model. The time-independent parameter store contains parameters for each query for the time-independent query model. The query analysis system also includes a generate query frequency table component 615 that analyzes the clickthrough logs and generates the data for the query frequency store.

The query analysis system includes a generate query model component 620 that controls the generating of the time-dependent query models and the time-independent query models. The generate query model component invokes a determine periodicity component 621 and a generate time-dependent query model component 622. The determine periodicity component generates the values of the frequency spectral for a query, invokes an identify peaks component 623 to identify the peaks within the frequency spectral, and determines the periodicities of the query. The generate time-dependent query model component generates the parameters for a time-dependent query model for a query and stores them in the time-dependent parameter store. The generate query model also invokes an identify causal queries component 624 and a generate time-independent query model component 625. The identify causal queries component identifies the candidate queries that are causally related to a target query by invoking an identify events component 626 and a calculate causal scores component 627. The identify events component identifies events within each query. The calculate causal scores component calculates the query causal score for a pair of queries. The identify causal queries component identifies the candidate queries. The generate time-independent query model component inputs the candidate queries and generates weights for the time-independent query model and stores an indication of the candidate queries and the weights as parameters in the time-independent parameter store.

The query analysis system also includes a predict frequency for time-dependent query component 631, a predict frequency for time-independent query component 632, a display frequency graph component 633, and a display event explanation component 634. The predict frequency for time-dependent query component inputs a query and predicts its frequency using a time-dependent query model (or prediction model). The predict frequency for time-independent query component inputs a query and predicts the frequency for that query using a time-independent query model. The display frequency graph component generates a graph for the past frequencies of a query and predicted frequencies that are predicted using either a time-dependent or time-independent query model. The display event explanation component analyzes the clickthrough data for a query and generates a report of the number of times that items of the search result for that query were selected by users.

The computing device on which the query analysis system is implemented may include a central processing unit, memory, input devices (e.g., keyboard and pointing devices), output devices (e.g., display devices), and storage devices (e.g., disk drives). The memory and storage devices are computer-readable media that may be encoded with computer-executable instructions that implement the query analysis system, which means a computer-readable medium that contains the instructions. In addition, the instructions, data structures, and message structures may be stored or transmitted via a data transmission medium, such as a signal on a communication link. Various communication links may be used, such as the Internet, a local area network, a wide area network, a point-to-point dial-up connection, a cell phone network, and so on.

Embodiments of the system may be implemented in and used with various operating environments that include personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, digital cameras, network PCs, minicomputers, mainframe computers, computing environments that include any of the above systems or devices, and so on.

The query analysis system may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, and so on that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments. In addition, the functions of the query analysis may be performed offline. For example, the query analysis system may generate new query models on a periodic basis and store the parameters for use in real time. Also, the generating of the query model may be performed by computing devices separate from computing devices that use the parameters of the model.

FIG. 7 is a block diagram that illustrates the logical organization of a data structure of the query frequency store in some embodiments. A data structure 700 may include a query table 701 with an entry for each query of a clickthrough log. Each entry contains the query along with a reference to a frequency count table 702. A frequency count table contains an entry for each interval represented by the clickthrough log. Each entry contains an identification of the interval and the frequency of that query during that interval. Each entry also contains a reference to a URL table 703 that contains an entry for each item selected by the searchers from the search results of that query during the interval. Each entry contains the URL of the item selected along with the count of the number of times that the search result item was selected.

FIG. 8 is a flow diagram that illustrates the processing of a create query model component of the query analysis system in some embodiments. The create query model component is invoked to determine the time dependency of a passed query and to generate a time-dependent query model or time-independent query model for the query. In block 801, the component invokes the determine time dependency component to determine the time dependency of the query. In decision block 802, if the query is time-independent, than the component continues at block 805, else the component continues at block 803. In block 803, the component invokes the generate time-dependent query model component to generate a time-dependent query model for the query. In decision block 804, if the error in the generated time-dependent query model satisfies an accuracy criterion, then the component returns an indication that the time-dependent query model is accurate, else the component returns an indication that the time-dependent query model is not accurate. In block 805, the component invokes the identify causal queries component to identify the candidate queries that are causally related to the query. In block 806, the component invokes the generate time-independent query model component to generate the time-independent query model for the query. One skilled in the art will appreciate that if the accuracy of a time-dependent query model for a query is not acceptable, then the query analysis system may generate a time-independent query model for that query.

FIG. 9 is a flow diagram that illustrates the processing of a determine time dependency component of the query analysis system in some embodiments. The component is passed a query and determines whether the query is time-dependent or time-independent. If the query is time-dependent, then the component returns the periodicities of the query. In block 901, the component calculates the mean frequency of the query. In block 902, the component centralizes the frequencies of the query by subtracting the mean frequency from each frequency. In block 903, the component invokes the identify peaks component to identify peaks within the frequency spectral of the query. In decision block 904, if no peaks were detected, then the component returns an indication that the query is time-independent, else the component continues at block 905. In block 905, the component calculates the periodicity for each peak and then returns the periodicities along with an indication that the query is time-dependent.

FIG. 10 is a flow diagram that illustrates the processing of the identify peaks component of the query analysis system in some embodiments. The identify peaks component is passed a query and identifies peaks within the frequency spectral of that query. In blocks 1001-1004, the component loops calculating a value of frequency spectral for various angular frequencies. In block 1001, the component initializes the angular frequency. In block 1002, the component calculates the value for the frequency spectral for the selected angular frequency. In decision block 1003, if all the angular frequencies have already been selected, then the component continues at block 1005, else the component continues at block 1004. In block 1004, the component selects the next angular frequency and then loops to block 1002 to calculate the corresponding value at that angular frequency. In blocks 1005-1010, the component loops identifying peaks. In block 1005, the component initializes the angular frequency and count of the number of peaks. In decision block 1006, if the value of the frequency spectral corresponding to the selected angular frequency is a peak, then the component continues at block 1007, else the component continues at block 1009. In block 1007, the component increments the number of peaks. In block 1008, the component sets the angular frequency of the peak. In decision block 1009, if all the angular frequencies have already been selected, then the component returns an indication of the number of peaks and the corresponding angular frequencies, else the component continues at block 1010. In block 1010, the component selects the next angular frequency and then loops to block 1006 to identify a peak.

FIG. 11 is a flow diagram that illustrates the processing of the generate time-dependent query model component of the query analysis system in some embodiments. The component is passed an indication of the angular frequencies of the peaks and generates and evaluates the accuracy of the model. In block 1101, the component generates the model parameters for each peak according to Equation 6. In block 1102, the component uses the model parameters to predict the frequency of the query at each interval for which the actual frequency was collected. In blocks 1103-1105, the component loops calculating the square of the differences between the actual frequency and the predicted frequency. In block 1103, the component selects the next interval. In decision block 1104, if all the intervals have already been selected, then the component continues at block 1106, else the component continues at block 1105. In block 1105, the component generates a running sum of the square of the differences and then loops to block 1103 to select the next interval. In blocks 1106-1108, the component loops aggregating the amplitude of the angular frequency for each peak. In block 1106, the component selects the next peak. In decision block 1107, if all the peaks have already been selected, then the component continues at block 1109, else the component continues at block 1108. In block 1108, the component accumulates the amplitude of the angular frequency and then loops to block 1106 to select the next peak. In block 1109, the component calculates the error according to Table 1. The component then returns an indication of the error.

FIG. 12 is a flow diagram that illustrates the processing of an identify causal queries component of the query analysis system in some embodiments. The component is passed a query and identifies candidate queries that are causally related to the query. In blocks 1201-1203, the component loops identifying events of each query. In block 1201, the component selects the next query. In decision block 1202, if all the queries have already been selected, then the component continues at block 1204, else the component continues at block 1203. In block 1203, the component invokes the identify events component to identify the events for the selected query and then loops to block 1201 to select the next query. The query analysis system represents each query by the sequence of its events. In blocks 1204-1206, the component loops calculating a query causal score for each query indicating its causal relatedness to the target query. In block 1204, the component selects the next query. In decision block 1205, if all the queries have already been selected, then the component continues at block 1207, else the component continues at block 1206. In block 1206, the component invokes a calculate query causal score component to generate a query causal score for the selected query and the target query. The component then loops to block 1204 to select next query. In block 1207, the component selects the queries with the highest scores as the candidate queries. The component then returns the selected queries.

FIG. 13 is a flow diagram that illustrates the processing of the identify events component of the query analysis system in some embodiments. The component is passed a query and identifies the events within the query. In block 1301, the component invokes the identify candidate events component to calculate the candidate events using a 3σ rule of Gaussian distribution. In block 1302, the component invokes the merge candidate events component to merge candidate events that overlap significantly. In block 1303, the component invokes the split candidate events component to split candidate events that have climaxes that are separated by deep valleys. The component then returns the candidate events as the event for the query.

FIG. 14 is a flow diagram that illustrates the processing of the identify candidate events component of the query analysis system in some embodiments. The component identifies candidate events as a sequence of intervals with frequencies above a baseline threshold with at least one frequency above a climax threshold. In some embodiments, the baseline threshold is a frequency that is greater than the mean frequency of the query by one standard deviation, and the climax threshold is greater than the mean frequency by three standard deviations assuming a Gaussian distribution. One skilled in the art will appreciate that other baseline and climax criteria may be used. In blocks 1401-1410, the component loops selecting each interval of the query and determining whether a sequence of intervals is a candidate event. In block 1401, the component selects the next interval. In decision block 1402, if all the intervals have already been selected, then the component returns the designated candidate events, else the component continues at block 1403. In decision block 1403, if the frequency of the selected interval is above the baseline threshold, then the component has detected the start of a sequence of interval above the baseline threshold and continues at block 1404, else the component loops to block 1401 to select the next interval. In block 1404, the component sets the start and end of what may be designated as a candidate event to the selected interval. In blocks 1405-1410, the component loops identifying at the sequence of intervals whose frequencies are above the baseline threshold and determining whether any of the frequencies above the climax threshold. In decision block 1405, if the frequency of the selected interval is above the climax threshold, then the component continues at block 1406, else the component continues at block 1407. In block 1406, the component designates the sequence of intervals as being a candidate event. In block 1407, the component selects the next interval. In decision block 1408, if all the intervals for the query have already been selected, then the component returns the candidate events, else the component continues at block 1409. In decision block 1409, if the frequency for the selected interval is above the baseline threshold, then the component continues at block 1410, else the component loops to block 1401 to select the next interval. In block 1410, the component adjusts the end of the sequence of intervals that are above the baseline threshold to the currently selected interval and then loops to block 1405 to select the next interval.

FIG. 15 is a flow diagram that illustrates the processing of the merge candidate events component of the query analysis system in some embodiments. The component is passed candidate events and merges the candidate events when they satisfy a merge events criterion such as that the sequence of their intervals overlaps significantly. In block 1501, the component selects the next candidate event. In decision block 1502, if all the candidate events have already been selected, then the component returns, else the component continues at block 1503. In block 1503, the component selects the next candidate event following the selected event. In decision block 1504, if all the next following events have already been selected, then the component returns, else the component continues at block 1505. In block 1505, if the selected event and the selected following events satisfy a merge events criterion, then the component continues at block 1506, else the component loops to block 1501 to select the next event. In block 1506, the component merges the selected event and the selected following event and then loops to block 1503 to select the next following event.

FIG. 16 is a flow diagram that illustrates the processing of the split candidate events component of the query analysis system in some embodiments. The component checks each candidate event to determine whether it should be split into multiple candidate events. In block 1601, the component selects the next candidate event. In decision block 1602, if all the candidate events have already been selected, then the component returns, else the component continues at block 1603. In block 1603, the component locates the initial climax of the selected candidate event. In blocks 1604-1608, the component loops locating the next climax of the selected event and determining whether it should be split. In block 1604, the component locates the next climax of the selected candidate event. In decision block 1605, if all the climaxes of the selected event have already been located, then the component loops to block 1601 to select the next event, else the component continues at block 1606. In block 1606, the component searches for a frequency between the selected climax and the next climax that satisfies a split event criterion. For example, the split event criterion may be satisfied when a frequency is below a threshold frequency indicating a deep valley of frequencies between the climaxes. In decision block 1607, if the split event criterion is satisfied, then the component continues at block 1608 to split the event. The component then loops to block 1604 to select the next climax.

FIG. 17 is a flow diagram that illustrates the processing of the calculate query causal score component of the query analysis system in some embodiments. The component is passed a pair of queries and calculates a score indicating that the first query of the pair causally precedes the second query of the pair. In block 1701, the component selects the next event of the first query. In decision block 1702, if all the events of the first query have already been selected, then the component continues at block 1707, else the component continues at block 1703. In block 1703, the component invokes a calculate event/query score component to generate a score indicating likelihood that the event causes events of the second query. In block 1704, the component calculates the area of the selected event. In block 1705, the component accumulates a numerator for generating the query causal score. In block 1706, the component accumulates a denominator for calculating the query causal score and then loops to block 1701 to select the next event. In block 1707, the component divides the numerator by the denominator to generate the query causal score and returns that score.

FIG. 18 is a flow diagram that illustrates the processing of the calculate event/query score component of the query analysis system in some embodiments. The component is passed an event and a query and generates a score indicating whether the event is a causal event of the query. In block 1801, the component selects the next event of the query that is after the passed event. In decision block 1802, if all such events have already been selected, then the component returns the maximum event causal score, else the component continues at block 1803. In block 1803, the component sets a numerator for calculating an event causal score based on the area of the events. In block 1804, the component sets a denominator to the maximum of the area of a passed event or the selected event. In block 1805, the component calculates the event causal score by dividing the numerator by the denominator. In block 1806, the component updates the evenVquery score to be the maximum of the event causal scores calculated so far. The component then loops to block 1801 to select the next event of the query.

FIG. 19 is a flow diagram that illustrates the processing of a display frequency graph component of the query analysis system in some embodiments. The component is passed a query and a range of intervals and displays a graph of past and predicted frequencies for the query. In block 1901, the component invokes the create query model to create either a time-dependent query model or time-independent query model for the query. In block 1902, the component displays the axes of the graph. In block 1903, the component displays a graph of the actual frequencies. In decision block 1904, if a model was generated, then the component continues at block 1905, else the component completes. In block 1905, the component predicts frequencies using the model. In block 1906, the component displays the predicted frequencies. In decision block 1907, if the model is a time-dependent query model, then the component displays periodicity information of the query in block 1908. The component then completes.

FIG. 20 is a flow diagram that illustrates the processing of the display event explanation component of the query analysis system in some embodiments. The display event explanation component receives a query and an interval range and displays a list of the top URLs selected by searchers using that query during the range. In block 2001, the component selects the next interval in the range. In decision block 2002, if all the intervals have already been selected, then the component continues at block 2007, else the component continues at block 2003. In block 2003, the component selects the next clickthrough entry. In decision block 2004, if all the clickthrough entries have already been selected for the selected interval, then the component loops to block 2001 to select the next interval, else the component continues at block 2005. In block 2005, the component updates the URL interval count for the URL of the selected entry. In block 2006, the component updates a URL count for the entire range for the URL of the selected entry and then loops to block 2003 to select the next clickthrough entry. In block 2007, the component sorts the URLs by count. In block 2008, the component generates an interval trend chart indicating how the frequency of each item changes at each interval. In block 2009, the component displays an indication of the URLs and interval trend chart and returns.

FIG. 21 is a flow diagram that illustrates the processing of the predict frequency for time-dependent query component of the query analysis system in some embodiments. The component is passed a query and an indication of a time interval. In block 2101, the component retrieves parameters for the time-dependent query model for the query. In block 2102, the component initializes the query frequency to the mean query frequency plus any background noise. In blocks 2103-2105, the component loops selecting the next periodicity and accumulating the frequencies for each periodicity. In block 2103, the component selects the next periodicity for the query. In decision block 2104, if all the periodicities have already been selected, then the component returns the frequency of the query, else the component continues at block 2105. In block 2105, the component aggregates the frequency for the selected periodicity based on Equation 1.

FIG. 22 is a flow diagram that illustrates the processing of the predict frequency for time-independent query component of the query analysis system in some embodiments. The component is passed a query and an interval and predicts the frequency of that query at that interval using a time-independent query model. In block 2201, the component retrieves the parameters for the time-independent model for the query. In block 2202, the component initializes the frequency for the query based on background noise. In block 2203, the component selects the next candidate query of the model. In decision block 2204, if all the candidate queries have already been selected, then the component returns the frequency of the query, else the component continues at block 2205. In block 2205, the component retrieves the frequency for the selected candidate query at the interval. In block 2206, the component accumulates the weighted sum of the candidate frequencies and then loops to block 2203 to select the next candidate query.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. Accordingly, the invention is not limited except as by the appended claims. 

1. A method in a computing device for determining a causal relationship between a first query and a second query, the method comprising: identifying first events of the first query and second events of the second query; for combinations of first events and second events, generating an event causal score indicating the causal relationship between the first event of the combination and the second event of the combination; and generating a query causal score indicating the causal relationship between the first event and the second event by aggregating the event causal scores of the combinations of events of the first query and the second query.
 2. The method of claim 1 wherein each event has an event period and the event causal score for a combination of a first event and a second event is based on overlap between the event period of the first event and the event period of the second event.
 3. The method of claim 1 wherein each event has an event area and the event causal score for a combination of a first event and a second event is based on intersection of the event area of the first event and the event area of the second event.
 4. The method of claim 3 wherein the event area of an event is based on an event period of an event and frequency of the query during the time period.
 5. The method of claim 1 wherein the event causal score between a first event and a second event is represented by the following: ${P\left( {e_{1} \prec e_{2}} \right)} = \left\{ \begin{matrix} 0 & {{if}\mspace{14mu} {t_{b}\left( e_{1} \right)}\mspace{14mu} {after}\mspace{14mu} {t_{b}\left( e_{2} \right)}} \\ \frac{{S\left( e_{1} \right)}\bigcap{S\left( e_{2} \right)}}{\max \left( {{S\left( e_{1} \right)},{S\left( e_{2} \right)}} \right)} & {{else}.} \end{matrix} \right.$
 6. The method of claim 1 wherein the generating of a query causal score includes generating event/query causal scores between first events and the second query indicating causal relationship between a first event and the second query and aggregating the event/query causal scores to generate the query causal score.
 7. The method of claim 6 wherein the event/query causal score is a maximum of the event causal scores between a first event and each of the second events.
 8. The method of claim 6 wherein the query score is a summation of an event area of each first event times the event/query causal score for the first event divided by a summation of the event area of each first event.
 9. The method of claim 1 wherein the generating of the query causal score is represented as follows: $\begin{matrix} {{P\left( {A \prec B} \right)} = \frac{\sum\limits_{i = 1}^{M^{A}}{{S\left( e_{i}^{A} \right)}{P\left( {e_{i}^{A} \prec B} \right)}}}{\sum\limits_{i = 1}^{M^{A}}{S\left( e_{i}^{A} \right)}}} \\ {= {\frac{\sum\limits_{i = 1}^{M^{A}}{{S\left( e_{i}^{A} \right)}{\max\limits_{1 \leq j \leq M^{B}}{P\left( {e_{i}^{A} \prec e_{j}^{B}} \right)}}}}{\sum\limits_{i = 1}^{M^{A}}{S\left( e_{i}^{A} \right)}}.}} \end{matrix}$
 10. The method of claim 1 including generating a query causal score for each of a plurality of queries indicating causal relationship between each of the plurality of queries and the second query and predicting events of the second query based on the query causal scores for the plurality of queries.
 11. A computer-readable medium encoded with instructions for causing a computing device to predict frequency of a target query, by a method comprising: for each of a plurality of queries, generating a query causal score indicating causal relationship between the query and the target query; selecting candidate queries for predicting events of the target query, the candidate queries being selected based on their query causal scores; learning a query model using frequencies of the candidate queries for predicting frequency of the target query; and calculating a predicted frequency for the target query by applying the query model to frequencies of the candidate query.
 12. The computer-readable medium of claim 11 wherein a multiple regression algorithm is used to learn the query model.
 13. The computer-readable medium of claim 11 wherein the query model is represented by the following: Q=β ₀+β₁ C _(1+β) ₂ C ₂+ . . . +β_(n) C _(n)+ξ.
 14. The computer-readable medium of claim 13 wherein the learning of the query model estimates a parameter for each query based on a solution to the following: $\left\{ {\begin{matrix} {q_{1} = {\beta_{0} + {\beta_{1}c_{11}} + {\beta_{2}c_{21}} + {{\ldots++}\beta_{n}C_{n\; 1}}}} \\ {q_{N} = {\beta_{0} + {\beta_{1}c_{1\; N}} + {\beta_{2}c_{2N}} + {{\ldots++}\beta_{n}{C_{nN}.}}}} \end{matrix}\quad} \right.$
 15. The computer-readable medium of claim 11 wherein the generating of a query causal score between a first query and the target query includes generating, for each first event of the first query, an event/query causal score between the first event and the target query and aggregating the event/query causal scores into the query causal score.
 16. The computer-readable medium of claim 15 wherein an event/query causal score for a first event and the target query is based on a maximum of event causal scores between the first event and each event of the target query.
 17. A computing device for predicting frequency of a target query, comprising: a query frequency store having frequencies of each of a plurality of queries at intervals; a component that identifies events within the queries; a component that selects as candidate queries those queries whose events have a likely causal relationship with events of the target query; a component that learns a query model using frequencies of the candidate queries for predicting a frequency of the target query; and a component that predicts the frequency of the target query by applying the query model to frequencies of the candidate queries.
 18. The computing device of claim 17 wherein the component that selects candidate queries makes the selection based on a query causal score indicating causal relationship between a candidate query and the target query, the query causal score based on an event/query causal score for each event of a candidate query indicating causal relationship between the event and the target query.
 19. The computing device of claim 17 wherein the component that learns a query prediction model learns parameters for combining frequencies of the candidate queries to predict the frequency of the target query.
 20. The computing device of claim 19 wherein the component that predicts the frequency generates a linear combination of the frequency of the candidate queries weighted by the learned parameters. 